Cloud-based applications require a high degree of automation regarding their IT\r\nresource management, for example, to handle scalability or resource failures. This\r\nautomation is enabled by cloud providers offering management interfaces accessed by\r\napplications without human interaction. The properties of clouds, especially pay-per-use\r\nbilling and low availability of individual resources, demand such a timely system\r\nmanagement. We call the automated steps to perform one of these management tasks a\r\nââ?¬Å?management flowââ?¬Â. Because the emerging behavior of the overall system is comprised of\r\nmany such management flows and is often hard to predict, we propose defining abstract\r\nmanagement flows, describing common steps handling the management tasks. These\r\nabstract management flows may then be refined for each individual use case. We cover\r\nabstract management flows describing how to make an application elastic, resilient\r\nregarding IT resource failure, and how to move application components between different\r\nruntime environments. The requirements of these management flows for handled\r\napplications are expressed using architectural patterns that have to be implemented by the\r\napplications. These dependencies result in abstract management flows being interrelated\r\nwith architectural patterns in a uniform pattern catalog. We propose a method by use of a\r\ncatalog to guide application managers during the refinement of abstract management flows\r\nat the design stage of an application. Following this method, runtime-specific management\r\nfunctionality and management interfaces are used to obtain automated management flows\r\nfor a developed application.
Loading....